Multi-device call notification silencing

ABSTRACT

A connection manager manages connections for associated user devices by determining whether an incoming connection has been answered at a user device, and if so then generating and transmitting silencing commands to associated user devices using first and second wireless communication modes, with one mode being faster. Connections can comprise phone calls, and modes can comprise push and Bluetooth® messaging. The connection manager can instruct device outputs to provide connection alerts, limited to visual alerts when an associated user device is active, listen for associated user device communications, and instruct device outputs to stop providing alerts when a silencing command is received. Further, a connection manager can receive a signal regarding a headset status, route an outside connection from a phone to the headset when the headset is active or to another device when the headset is not active, detect a change in headset status, and reroute the connection accordingly.

CROSS-REFERENCE TO RELATED APPLICATION

This Application is a continuation of U.S. patent application Ser. No.15/816,759, entitled “MULTI-DEVICE CALL NOTIFICATION SILENCING,” filedNov. 17, 2017, issued as U.S. Pat. No. 10,218,840 on Feb. 26, 2019,which is a continuation of U.S. patent application Ser. No. 15/170,805,entitled “MULTI-DEVICE CALL NOTIFICATION SILENCING,” filed Jun. 1, 2016,issued as U.S. Pat. No. 9,826,089 on Nov. 21, 2017, which claims thebenefit of U.S. Provisional Application No. 62/172,025, entitled “CALLMANAGEMENT BETWEEN MULTIPLE USER DEVICES,” filed Jun. 5, 2015, and U.S.Provisional Patent Application No. 62/172,028, entitled “MULTI-DEVICECALL NOTIFICATION SILENCING,” filed Jun. 5, 2015, the contents of whichare incorporated by reference herein in their entirety for all purposes.

Moreover, this application is related to U.S. patent application Ser.No. 15/170,705, entitled “CALL MANAGEMENT BETWEEN MULTIPLE USERDEVICES,” filed Jun. 1, 2016, issued as U.S. Pat. No. 9,848,079 on Dec.19, 2017, the entire contents of which are incorporated herein byreference.

FIELD

The described embodiments relate generally to communications usingelectronic devices, including systems and techniques for managing callsbetween multiple associated user devices.

BACKGROUND

Recent technological advances give rise to situations in which anindividual has multiple different active electronic devices, often atthe same general location and at the same time. In addition to a smartphone, a user may also simultaneously have a headset, a tablet device, alaptop computer, a desktop computer, a portable media player, and/or oneor more other electronic devices, some or all of which may be able toconduct wireless communications.

Oftentimes, a telephone call or other communication may come in to asmart phone of a user while the phone is nearby but not with the user,or when it may be otherwise inconvenient to answer the call on the phoneitself. However, the user is unable to take or reject the call throughanother device. In other situations, a user may wish to initiate a newcall or otherwise transfer an existing call between user devices thatinclude more than just the smart phone itself. Nonetheless, if evenpossible, this can be an inconvenient process using existingcommunication systems and methods, and can often result in delays ordropped calls.

SUMMARY

Representative embodiments set forth herein disclose various systems andtechniques for intelligently and efficiently managing calls and othercommunications between multiple associated user devices. In particular,the embodiments set forth various systems and techniques for allowing aconnection manager executing on a user device to manage outsideconnections in various ways. This connection manager can be triggered tocarry out its connection management operations in an automated manner(e.g., according to user settings) or in a reactive manner (e.g., inresponse to receiving a user input or command). According to someembodiments, a connection manager can operate by (1) routing an outsideconnection from a user device to a first associated user device when thefirst device is active or to a second associated user device when thefirst device is not active, (2) detecting a change in the status of thefirst device, and/or in response (3) rerouting the outside connectionfrom one of the first or second devices to the other.

Under various embodiments, a connection manager can also, oralternatively, operate by (1) determining when an incoming connection isanswered at a user device or an associated user device, (2) sending asilencing command to associated user devices using multiple differentcommunication modes when the incoming connection is answered at the userdevice, and (3) instructing the user device to stop providing anincoming call alert when the incoming connection is instead answered atan associated user device. A different connection manager can be locatedon each of a plurality of user devices, such that each separate userdevice can be managed by a separate connection manager.

This Summary is provided only for purposes of summarizing some exampleembodiments so as to provide a basic understanding of some aspects ofthe subject matter described herein. Accordingly, it will be appreciatedthat the above-described features are only examples and should not beconstrued to narrow the scope or spirit of the subject matter describedherein in any way. Other features, aspects, and advantages of thesubject matter described will become apparent from the followingDetailed Description, Figures, and Claims.

Other aspects and advantages of the embodiments described herein willbecome apparent from the following detailed description taken inconjunction with the accompanying drawings which illustrate, by way ofexample, the principles of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The included drawings are for illustrative purposes and serve only toprovide examples of possible structures and arrangements for thedisclosed systems and techniques for intelligently and efficientlymanaging calls and other communications between multiple associated userdevices. These drawings in no way limit any changes in form and detailthat may be made to the embodiments by one skilled in the art withoutdeparting from the spirit and scope of the embodiments. The embodimentswill be readily understood by the following detailed description inconjunction with the accompanying drawings, wherein like referencenumerals designate like structural elements.

FIG. 1 illustrates in block diagram format a set of overlapping networksfor an exemplary wireless communication user device according to variousembodiments of the present disclosure.

FIG. 2 illustrates in block diagram format an exemplary system ofdifferent wireless networks and devices according to various embodimentsof the present disclosure.

FIG. 3 illustrates in block diagram format a detailed view of particularexemplary components in a system of different wireless networks anddevices according to various embodiments of the present disclosure.

FIG. 4 illustrates a sequence diagram for an exemplary management of anincoming connection at a set of associated user devices having a relayedarrangement according to various embodiments of the present disclosure.

FIG. 5 illustrates a sequence diagram for an exemplary management of anincoming connection at a set of associated user devices having norelayed arrangement according to various embodiments of the presentdisclosure.

FIG. 6 illustrates a flowchart of an exemplary method performed by aconnection manager for managing outside connections on a set ofassociate user devices according to various embodiments of the presentdisclosure.

FIG. 7 illustrates a sequence diagram for an exemplary management of anincoming connection at a set of associated user devices having an activedevice according to various embodiments of the present disclosure.

FIG. 8 illustrates a flowchart of an exemplary method performed by aconnection manager for managing outside connections on a set ofassociated user devices having an active device according to variousembodiments of the present disclosure.

FIG. 9 illustrates in block diagram format an alternative exemplarysystem of wireless networks and devices according to various embodimentsof the present disclosure.

FIG. 10 illustrates a state diagram of exemplary states and transitionsfor the system of FIG. 9 according to various embodiments of the presentdisclosure.

FIG. 11 illustrates a flowchart of an exemplary method performed by aconnection manager on a user device for managing outside connections forthe user device and a set of associated user devices according tovarious embodiments of the present disclosure.

FIG. 12 illustrates in block diagram format an exemplary computingdevice that can be used to implement the various components andtechniques described herein according to various embodiments of thepresent disclosure.

DETAILED DESCRIPTION

Representative applications of apparatuses, systems, and methodsaccording to the presently described embodiments are provided in thissection. These examples are being provided solely to add context and aidin the understanding of the described embodiments. It will thus beapparent to one skilled in the art that the presently describedembodiments can be practiced without some or all of these specificdetails. In other instances, well known process steps have not beendescribed in detail in order to avoid unnecessarily obscuring thepresently described embodiments. Other applications are possible, suchthat the following examples should not be taken as limiting.

Oftentimes, a telephone call or other communication may come in to adevice, e.g., a smart phone or other user device, while the device isnearby but not with the user, or when it may be otherwise inconvenientto answer the call or communication on the receiving device. In suchsituations, another associated device (e.g., registered with the sameaccount) may be a more convenient or preferable device for responding toor otherwise acting on the incoming call or communication. In othersituations, a user may wish to initiate a new call from, or otherwisetransfer an existing call between, one or more user devices that includemore than just a smart phone or original receiving device.

Accordingly, the embodiments set forth herein provide various systemsand techniques for allowing a connection manager executing on a userdevice to manage outside connections various ways. This connectionmanager can be triggered to carry out its connection managementoperations in an automated manner (e.g., according to configuredsettings) or in a reactive manner (e.g., in response to receiving acommand, such as user input). According to some embodiments, aconnection manager can operate by (1) routing an outside connection froma user device to a first associated user device when the first device isactive or to a second associated user device when the first device isnot active, (2) detecting a change in the status of the first device,and in response (3) rerouting the outside connection from one of thefirst or second devices to the other.

Under various embodiments, a connection manager can also, oralternatively, operate by (1) determining when an incoming connection isanswered at a user device or an associated user device, (2) sending asilencing command to associated user devices using multiple differentcommunication modes when the incoming connection is answered at the userdevice, and (3) instructing the user device to stop providing anincoming call alert when the incoming connection is instead answered atan associated user device. A different connection manager can be locatedon each of a plurality of user devices, such that each separate userdevice can be managed by a separate connection manager.

Accordingly, the foregoing approaches provide systems and techniques forintelligently and efficiently managing outside connections betweenmultiple associated user devices. A more detailed discussion of thesesystems and techniques is set forth below and described in conjunctionwith FIGS. 1 through 12, which illustrate detailed diagrams of systemsand methods that can be used to implement these systems and techniques.

Wireless communication devices, and mobile devices in particular, canincorporate multiple different radio access technologies to provideconnections through different wireless networks that offer differentservices and/or capabilities. A central wireless communication devicecan include hardware and software to support a wireless personal areanetwork (“WPAN”) according to a WPAN communication protocol, such asthat which has been standardized by the Bluetooth® special interestgroup (“SIG”). The central wireless communication device can discovercompatible peripheral or associated wireless communication devices andcan establish connections to these peripheral or associated wirelesscommunication devices in order to provide specific communicationservices through a WPAN. In some situations, the central wirelesscommunication device can act as a communications hub that providesaccess through a wireless local area network (“WLAN”) and/or through awireless wide area network (“WWAN”) to a wide variety of services thatcan be supported by various applications executing on the centralwireless communication device.

Many applications and services can provide for alert notifications topresent supplemental information to a user of the central wirelesscommunication device, such as to indicate initiation of a proposedservice connection (voice, video, Internet messaging, teleconferencing,etc.), to catalog one or more events (email, voice mail, reminders,appointments, etc.), or to indicate near real time information (stock,weather, sports, news, etc.). Alert notifications can be presented onthe mobile wireless communication device in accordance with any numberof priorities and/or preferences, such as on demand (e.g., in responseto a user input), as an overlay (e.g., as an indicator associated with agraphical icon), or as an interrupt (e.g., as a pop-up message). Analert notification service operating on a central wireless communicationdevice can interact with an alert notification client operating on aperipheral or associated wireless communication device to provideinformation about various alert notifications available on the centralwireless communication device to a user through the peripheral orassociated wireless communication device. The alert notification clienton the peripheral or associated wireless communication device can bedefined as a profile for a WPAN wireless communication protocol, whichcan be, for example, a Bluetooth Low Energy (“BTLE”) wirelesscommunication protocol. The alert notification BTLE profile can providea wide array of information for the peripheral or associated wirelesscommunication device to present, e.g., to a user, and also mechanismsfor providing and/or receiving alert notifications.

The alert notification profile (and service) can provide for anefficient transfer of information using a WPAN wireless communicationprotocol, while adding a capability for a bi-directional exchange ofmessages between the peripheral or associated wireless communicationdevice (acting as a client) and the central wireless communicationdevice (acting as a server). An event associated with an application(e.g., a proposed connection, one or more new or existing messages, aset of locally or remotely generated information) can prompt an alertnotification at the central wireless communication device. A user oroperator can configure one or more applications and/or categories ofapplications to provide alert notifications that contain all or a subsetof information available at the central wireless communication device tothe peripheral or associated wireless communication device. In somesituations, this can include notifications to multiple peripheral orassociated wireless communication devices. In addition, the alerts canbe received independently by a number of associated wirelesscommunication devices. For example, a text message can be received ateach wireless communication device on which the account is active, andthese wireless communication devices may separately receive the textfrom a server or the central wireless communication device.

The various embodiments described herein can involve wirelesscommunications using one or more wireless technologies or protocols,such as, for example, a Bluetooth® WPAN communication protocol, betweena set of associated wireless communication devices, which can includeone or more user devices. Communications using this WPAN and/or otherwireless communication protocols can be made between one or more centralserver wireless devices and the set of associated wireless communicationdevices. In various situations, one or more of the associated userdevices can function as a central wireless communication device for WPANpurposes, and can then communicate with one or more of the otherassociates user devices accordingly. For example, various alerts andcommands can be sent between associated user devices using a WPANaccording to the embodiments disclosed herein. Further, it will beunderstood that all communications discussed herein can comprisewireless communications unless stated otherwise.

Turning first to FIG. 1, a set of overlapping networks for a wirelesscommunication user device is illustrated in block diagram format. Userdevice 110 can include a combination of hardware and software to providewireless connections using one or more different wireless networksalone, separately, or in combination, such as set of overlappingnetworks 100. The user device 110 can represent a device having wirelesscommunications capacity, such as a smart phone (e.g., an iPhone®), atablet device (e.g., an iPad®), a wearable device (e.g., an AppleWatch®), a portable media player (e.g., an iPod®), a laptop computer(e.g., a MacBook®), or a desktop computer (e.g., an iMac®), among otherpossible devices. Additional user devices can include a wirelessheadset, a vehicle sound system, a digital television, a digital mediarecorder, or any other suitable device capable of wirelesscommunications.

The user device 110 can include hardware and software to providecommunication using a WPAN 104, which can provide power efficientconnections while operating over a relatively shorter range. WPANconnections can typically provide for connecting the user device 110 toperipheral and associated wireless communication devices, such asheadsets, earpieces, supplemental display devices, and supplementalinput/output devices, for example. A representative WPAN 104 can operatein accordance with a communication protocol specified by the BluetoothSIG, for example. The user device 110 can also include hardware andsoftware to provide communication using a WLAN 106 that can provide ahigher data rate and a greater operating range than a WPAN 104. The userdevice 110 can include separate and/or shared hardware and softwareelements for the WPAN 104 and the WLAN 106. Both the WPAN 104 and WLAN106 can operate as “local” networks. The user device 110 can alsoinclude additional hardware and software to provide a WWAN 108capability, such as to interconnect with one or more cellular networks.The user device 110 can provide a multitude of services using one ormore connections through its wireless networking capabilities, and analert notification center on the user device 110 can provide alertnotifications to a user for one or more services. In addition, localapplications on the user device 110 can generate alert notifications toprovide additional information and alerts to the user and/or other userdevices. Alert notifications and related communications can be receivedfrom and/or transmitted to associated devices over any or all of WPAN104, WLAN 106, and WWAN 108.

FIG. 2 illustrates in block diagram format an exemplary system ofdifferent wireless networks and devices according to various embodimentsof the present disclosure. System 200 can include a receiving wirelesscommunication user device 210 that can be interconnected through severaldifferent wireless communication technologies to an external set ofnetworks and to a set of peripheral or associated local wirelesscommunication user devices 220A, 220B, and 220C. The user device 210 canbe a “central” device for WPAN purposes, and can receive informationfrom one or more packet switched networks and/or from one or morecircuit switched networks, the combination of which is represented inFIG. 2 as a combination of a public switched telephone network (“PSTN”)and the “Internet” 205. The user device 210 can use a WWAN connection208 provided through a wireless communication network 207 to access abroad variety of services (e.g., voice calls, text messages, dataaccess, video calls, multimedia messaging, and media streaming).Similarly, the user device 210 can use a WLAN connection 206 providedthrough a wireless access point 202 interconnected to a broadbandcommunication network 203 to access a similar wide range of services.The broad set of services provided through the WWAN connection 208and/or through the WLAN connection 206 can generate one or more alertnotifications associated with the services or with applications executedby user device 210 that access and/or use the services. In addition, theuser device 210 can use one or more WPAN connections 204 to one or morenearby peripheral or associated user devices 220A, 220B, 220C, asillustrated in FIG. 2.

Each of the associated user devices 220A, 220B, 220C illustrated in FIG.2 can provide output display capabilities as well as input responsecapabilities to allow a user of the user device 210 to interact withvarious services or otherwise relay connections or communications therethrough, such as through one or both of a WLAN connection 206 or WPANconnection 204. For example, any of associated user devices 220A, 220B,220C can provide call relay functionality for an incoming phone call orother connection to user device 210, such that the user can accept theincoming call or other connection at any of associated user devices 210,220A, 220B, or 220C. Such call relay functionality can be provided byway of various WLAN connections to a host server (e.g., iCloud) via acommon wireless access point 202, or by the various WPAN connections204, for example. In addition, one, some or all of associated userdevices 220A, 220B and/or 220C can be standalone independent userdevices that are able to operate independently of user device 210. Inone specific non-limiting embodiment, associated user device 220A can bea desktop computing device, associated user device 220B can be anelectronic watch device (or other “wearable”), and associated userdevice 220C can be a tablet device. It will be readily appreciated thatother types and arrangements of wireless communication devices can beused, and that fewer or more than three such devices can be localwireless communication user devices associated with user device 210. Asdescribed further below, alert notifications may be collectivelyprocessed by wireless communication user devices 210 and 220 in thesystem in FIG. 2.

Continuing with FIG. 3, a detailed view of particular exemplarycomponents in a system of different wireless networks and devices isshown in block diagram format. Similar to the foregoing example, system300 can include a wireless user device 310 and a set of local wirelessassociated user devices 320. While three associated user devices 320A,320B, 320N are shown in FIG. 3 for purposes of illustration, it will beappreciated that there can alternatively be one, two, four, or more userdevices that can be in the set of associated user devices 320. In somearrangements, the set of associated user devices can include the userdevice 310 too. User device 310 can again be a smart phone, a tabletdevice, a wearable device, a portable media player, a laptop computer, adesktop computer, or other computing device capable of wirelesscommunication. Each of associated user devices 320 might also be a smartphone, a tablet device, a wearable device, a portable media player, alaptop computer, a desktop computer, a wireless peripheral that servesuser device 310, or other computing device capable of wirelesscommunication. User device 310 can be adapted for wirelesscommunications using one or more: WWAN connections 308, WLAN connections306, and/or WPAN connections 304. Communications between user device 310and any or all of associated user devices 320 can be by way of WPANconnections 304. One, some, or all of the associated user devices 320are also able to communicate with each other, such as by way of WPANconnections 304. In addition, user device 310 and one or more of theassociated user devices 320 can communicate using WLAN connections 306with each other, a server, and/or a wireless access point 302.

In various embodiments, user device 310 can be a central wirelesscommunications device with respect to the remainder of the set ofassociated user devices 320, such as for a call relay arrangement, aWPAN connection 304 arrangement, or both. In addition, or alternatively,each of user devices 310 and 320 can simply be a peer device withrespect to the other user devices. In some arrangements, one or more ofthe other associated user devices 320 can be a central wirelesscommunications device with respect to the other associated user devices,which may or may not include user device 310, such as for a call relayarrangement, a WPAN connection 304 arrangement, or both.

As shown in FIG. 3, the user device 310 can have a processor 312, anassociated memory 314 communicatively coupled to the processor 312, anda connection manager 316 communicatively coupled to the processor 312(and thereby to the memory 314). The processor 312 can be configured toimplement the connection manager 316, and the connection manager 316 canbe adapted to manage connections for the user device 310 and the set ofassociated user devices 320. Each of the associated user devices 320 canalso similarly have its own separate processor 322A through 322N,associated memory 324A through 324N, and connection manager 326A through326N. Each separate processor 322 can similarly be configured toimplement its respective connection manager 326, which similarly can beadapted to manage connections for its respective user device 320 withany/all of the rest of the user device 310 and remaining set ofassociated user devices 320. Each connection manager 316 and 326 can beimplemented as a software program, a module, or a component that resideson and/or remotely from its respective user device. Each connectionmanager 316 and 326 can similarly be adapted to manage connections in avariety of ways, such that it will be understood that functionalitydiscussions and references to connection manager 316 specifically canalso extend equally to every other connection manager 326. Further, itwill be understood that references to connection managementfunctionality, features, statuses, and the like that are made withrespect to a specific user device may specifically apply to theconnection manager for that user device.

In some arrangements, any of the user device 310 and the variousassociated user devices 320 can be able to answer a call or otherconnection that is incoming to or arriving specifically at user device310, such as through a call relay or known user device groupingarrangement. Similarly, any of the user device 310 and the variousassociated user devices 320 can be able to respond to any other suchalert or notification received at or directed to any of the otherassociated devices. Under such an arrangement, a call or otherconnection or alert/notification coming in to user device 310, such asusing WWAN connection 308, can be relayed to a local server or othergrouped device managing entity, such as using a WLAN connection 306 to alocal access point 302. The incoming call orconnection/alert/notification can then be broadcast from the localserver or other grouped device managing entity to all of the userdevices 310 and 320, such as using various WLAN connections 306, uponwhich all of the user devices may then ring, flash lights, and/orprovide other alerts (visual, audible, and/or haptic) that the call orconnection/alert/notification is incoming and can be answered at orresponded to at any alert providing user device.

In the event that the incoming connection is answered (or responded to)at the user device 310 or any of the associated user devices 320, thenthe actual answering device can typically send a “connection answered”notification or status update so that all of the other user devices canstop ringing and/or providing other incoming connection alerts. Such a“call or connection answered” alert or status update can be sent using afirst mode of communication to the other user devices. This first modeof communication can be, for example, in the form of a push message tothe local server or other grouped device managing entity, such as byusing a WLAN connection 306 via local access point 302. The local serveror other group managing entity can then push the “call or connectionanswered” notification or status from local access point 302 using aWLAN connection 306 to each of the other individual non-answering userdevices 310 and 320 so that those other non-answering user devices canstop providing alerts. These WLAN connections 306 can be in the form oflocalized Wi-Fi connections, for example. As will be readilyappreciated, this push messaging relay via another server, device, orentity can take an elapsed time of 1-2 seconds or more on average, suchthat many of the user devices 310 and 320 continue to ring or providealerts for a 1-2 seconds or more after the connection has been answeredat one of the user devices. This delay or latency can be annoying orcumbersome in some instances, such that a faster alert silencingapproach for the remaining user devices may be desirable.

Accordingly, a second faster mode of communication can be used toprovide a “call or connection answered” notification, alert, or statusupdate to the remaining user devices in a set of associated userdevices. Alternatively, or in addition, a “silencing command” can beprovided to the remaining user devices using this second mode ofcommunication, which can be using one or more suitable WPAN connections304. Such WPAN connections 304 can be, for example, BTLE, otherBluetooth®, or other short range wireless connections that traveldirectly from user device to user device (“peer-to-peer”), for example.These “connection answered” alerts and/or “silencing commands” or alertscan generally be broadcast by the answering user device using BTLE oranother short range wireless protocol for a short period of time, suchthat all nearby user devices equipped to receive that form ofcommunication (e.g., BTLE alerts or communications) can receive theconnection answered alerts and/or silencing commands in that manner. Theshort period of time for this broadcast of a silencing command usingBTLE (or other form of short range wireless communication) can be, e.g.,on the order of about one to ten seconds. For example, in someimplementations, the command notifying other (neighboring) devices tocease outputting an alert associated with a given event can betransmitted for approximately two seconds. Because the transmission of aBTLE or similar alert or command can be direct from user device to userdevice, the overall transmittal time can be much faster than a pushmessage that travels indirectly, e.g., through the cloud or othercentral entity. In various embodiments, the total transmittal time usingthis second mode of communication can be on the order of about 200milliseconds. Under this arrangement, the non-responding (e.g.,non-answering) user devices can be silenced much more quickly.

Although a “connection answered” and/or “silencing command” can be sentusing BTLE, such that other user devices can be silenced faster, it maybe preferable in many embodiments to continue to send push messages thatthe connection has been answered. For example, there can be situationswhere a nearby user device is able to receive the push messages, such asusing Wi-Fi or another suitable WLAN connection 306, but for some reasondoes not also get the BTLE alert or silencing command, such as using aWPAN connection 304. Accordingly, such a nearby user device would thenstill be silenced, albeit over the delay or longer period of time thatit takes for the push message to arrive. Also, associated devicesoutside of the short range WPAN connection 304 can be silenced by thecommunication over the WLAN connection 306. In addition, otherinformation or commands can also be sent as push messages from thecentralized server or other device via the WLAN connection 306. Further,communications using the WLAN connections 306 can be bidirectional innature, while the BTLE alerts or commands using the WPAN connections 304do not need to be answered or even acknowledged. No handshake orbidirectional communication between user devices is necessary for suchBTLE alerts or communications. Accordingly, in many embodiments thedirect device to device communications using WPAN connections 304 cansimply be “silencing commands” or alerts from the answering device,which can be in the form of BTLE broadcasting advertisements, forexample.

Turning next to FIG. 4, a sequence diagram for an exemplary managementof an incoming connection at a set of associated user devices having arelayed arrangement is illustrated according to various embodiments ofthe present disclosure. In arrangement 400, a user device 410 can be acentral communication device for incoming connections 431 at user device410 for itself and a set of local associated user devices 420. Incomingconnections 431 can originate from an outside network 407, such as usinga WWAN and/or another suitable connection, and a local server 402 canmanage communications locally for all of the user devices 410 and 420.Server 402 can be adapted to communicate with user devices 410 and 420in a variety of ways, such as by push messaging, for example. Each ofuser devices 410 and 420 can be any wireless capable communicationdevice, such as, for example, a smart phone, a tablet device, a wearabledevice, a portable media player, a laptop computer, a desktop computer,or a wireless peripheral device that serves one of the other userdevices, among other possible wireless communication devices. Incomingconnection 431 can be any suitable connection, such as, for example, avoice call, a video call, an Internet message, a teleconference, a pushmessage, a text message, a data transfer, an e-mail, a voice mail, acalendar reminder, an invite request, an appointment notification, orany other suitable form of wireless communication.

As one non-limiting example and for purposes of illustration, userdevice 410 can be a smart phone, outside network 407 can be a cellularservices provider, incoming connection 431 can be a phone call, server402 can be a local grouped devices management server (e.g., iCloud), andexactly two associated user devices 420A and 420N can be a desktopcomputing device and a tablet device, respectively, adapted as relaydevices capable of answering calls directed to user device 410. Theincoming connection 431 can thus be answered at any of user devices 410,420A, or 420N, such as by way of a registered and grouped devicearrangement. It will be understood that many other types, forms, and/orarrangements of devices, networks, and/or connections may also apply forthis non-limiting example that is provided for purposes of illustration.Further, only one associated user device 420A or many more associateduser devices 420 may be present in a particular arrangement, such asarrangement 400.

In various situations, such as for the present example being discussed,incoming connection 431 can be a connection that can be answered by auser. In addition, it will again be understood that any actions taken byany of the user devices 410, 420A, or 420N can be performed or directedby the respective connection manager for that user device.

At a first sequence event 430, an incoming connection 431 can be sent touser device 410 from an outside network 407. Again for purposes ofdiscussion, incoming connection 431 will be referred to as a phone callor call, although any of the other types or forms of connections (e.g.,messaging, conferencing, streaming, etc.) may similarly apply.Accordingly, a connection manager for user device 410 can receive anotification that the incoming connection 431 is arriving at the userdevice 410. At a following sequence event 440, the user device 410 cannote that the incoming connection 431 is arriving and send anotification 441 that the incoming connection 431 is arriving to theserver 402. This can be done by way of a push message sent using a WLANcommunication, such as Wi-Fi, for example.

At a subsequent sequence event 445, the server 402 can note that theincoming connection 431 is arriving and send notifications 446 that theincoming connection 431 is arriving to the associated user devices 420A,420N. This can also be done by way of push messages sent using WLANcommunications, such as Wi-Fi, for example. Accordingly, respectiveconnection managers for each of associated user devices 420A and 420Ncan receive a notification that the incoming connection 431 is arriving.This can be with respect to arriving at the user device 410 and/or atthe respective associated user device 420A or 420N. At this point, everyuser device 410, 420A, and 420N can be aware that there is an incomingconnection 431 that can be answered at any of user devices 410, 420A,and 420N.

At sequence event 450, each of user devices 410, 420A, and 420N can notethat the incoming connection 431 is arriving and in response can provideone or more physical alerts or notifications that there is an incomingconnection 431, can determine whether the incoming connection 431 hasbeen answered at itself, and can listen for communications from any ofthe other user devices 410, 420A, and 420N. Each of these processes canoccur in parallel at a given user device 410, 420A, 420N, and/or each ofthese processes can continue until the incoming connection 431 is gone,until the incoming connection 431 is answered at one of the user devices410, 420A, or 420N, or until another end condition occurs. Thesedifferent processes can end differently and/or at different times fromeach other and across different user devices depending upon specificcircumstances. Also, sequence event 450 may start earlier for userdevice 410, e.g., immediately upon user device 410 learning thatincoming connection 431 is arriving. Similarly, sequence event 450 foreach of associated user devices 420A and 420N may start upon thatrespective user device learning about incoming connection 431.Accordingly, a slightly time staggered implementation may take place ateach user device for the parallel processes of providing physicalalerts, determining whether the connection has been answered at itself,and listening for communications from other devices.

Physical alerts can be provided at each respective user device 410,420A, and 420N. This can happen, for example, by way of each respectiveconnection manager instructing one or more output components on itsrespective user device to provide an alert that the incoming connection431 is arriving and has not been answered. Physical alerts can compriseaudible alerts (e.g., ringing), haptic alerts (e.g., vibration), and/orvisual alerts (e.g., blinking lights or screen indicators). Each userdevice 410, 420A, 420N can listen for communications using multiplecommunication modes, such as first and second communication modes. Afirst communication mode can be, for example, Wi-Fi or other WLANcommunications, which may take the form of push messages that comeindirectly from another user device 410, 420A, 420N, such as by way ofserver 402. A second different communication mode can be, for example,Bluetooth® or other WPAN communications, which may take the form of BTLEalerts, advertisements, and/or commands that come directly from anotheruser device 410, 420A, 420N.

At sequence event 460, incoming connection 431 can be answered atassociated user device 420A. This can represent, for example, a relayedphone call being answered at a desktop computer associated with a smartphone in one specific arrangement. Other arrangements mightalternatively apply, and it will be readily appreciated that incomingconnection 431 could instead have been answered at any of the other userdevices 410, 420N, with the following messages, events, and outcomesthen changing correspondingly. When the incoming connection 431 isanswered at user device 420A, a connection manager for that user device420A can determine that the incoming connection 431 has indeed beenanswered there, can generate a silencing command, and can transmit thesilencing command using first and second wireless modes ofcommunication. The silencing command can take a variety of forms, suchas embedded in a “call answered” push message and/or embedded in a BTLEalert or advertisement, for example.

Thus, sequence event 460 can also include a “call answered” notification461 that is sent from the user device 420A (e.g., answering device)directly to the server 402. This can again be done by way of a pushmessage sent using a WLAN communication, such as Wi-Fi, for example.Notification 461 can include the silencing command therein, or it may beinherent to a “call answered” notification that other user devices arecommanded to be silenced. Sequence event 460 can thus also include a“silencing command” notification 462 that is sent from the user device420A (e.g., answering device) directly to the other user devices 410,420N (e.g., non-answering devices). This can be done by way of a BTLEalert or advertisement sent using a WPAN communication, for example.Notification 462 can include the silencing command therein, and can takethe form of a WPAN broadcast, e.g., transmitted periodically,occasionally, or continuously for a range of durations from less thanone second to up to ten seconds, such as for about two seconds in someimplementations. Again, this form of direct device to devicecommunication can be relatively fast, such that the transmittal time ison the order of about 200 milliseconds.

Notification 462 containing a silencing command can be received as anincoming silencing command at each of non-answering user devices 410 and420N, whereupon those devices can then stop providing physical alertsthat the incoming connection 431 is arriving and has not yet beenanswered. In particular, the connection manager for each of theserespective devices 410, 420N can receive the incoming silencing commandand instruct its respective output component(s) to stop providingalert(s). The connection manager for the answering user device 420A canalso similarly instruct its respective output component(s) to stopproviding alert(s) when the incoming connection 431 is answered at userdevice 420A. Accordingly, user device 420A can then be at a state 463where the incoming connection 431 has been answered there and physicalalerts regarding the incoming connection 431 have been stopped, whileuser devices 410 and 420N can then be at a state 464 where physicalalerts regarding the incoming connection 431 have been stopped.

At sequence event 470, the server 402 can note that the incomingconnection 431 has been answered and can send or forward “call answered”notifications 471 to each of the non-answering user devices 410 and420N. This can again be done by way of a push message sent using a WLANcommunication, such as Wi-Fi, for example. These “call answered”notifications 471 can include an actual or inherent “silencing command,”in addition to other call answered information. Additional informationcan include a confirmation that the call or incoming communication wasactually answered at another user device, as well as which other userdevice answered. While the silencing command notifications 462 above cantypically arrive at each non-answering user device 410, 420N faster thanthe call answered notifications 471 do, these call answerednotifications can provide additional information as well as a backupsilencing command in the event that a given user device does not receivea separate silencing command notification 462 for any reason. In otherwords, silencing command notifications 462 can be used solely as afaster way to tell other user devices to “silence” or otherwise stopproviding physical alerts, while call answered notifications 471 canprovide additional information and functionality. Accordingly, userdevice 410 may stop providing alerts upon receiving a silencing commandnotification 462, but may wait until receiving a call answerednotification 471 to confirm and actually process which other user devicehas answered the incoming connection 431 to act accordingly.

It will be appreciated then that silencing commands can be a relativelyfaster and lower-level way to have various user devices stop providingphysical alerts. Such silencing commands can be sent in response to anincoming connection being answered at another user device, and can alsobe sent in response to various other events. For example, a user cansend such a faster and lower-level silencing command via a user inputremotely from another device, rather than waiting for a push message tosend a silencing command, or even for the incoming connection to beanswered at any user device. Other inputs and settings can also be usedto control the sending of these relatively faster and lower-levelsilencing commands between user devices according to other preferences,events, and occurrences as well.

At sequence event 480, the user device 410 can note that the incomingconnection 431 has been answered can send a notification 481 to theoutside network 407 that the incoming connection 431 has been answeredor accepted, upon which a connection can then be established between theoutside network 407 and the user device 410 at sequence event 490. Thisestablished connection can be made from the outside network 407 to theuser device 410, where the connection is then relayed to the associateduser device 420A where the incoming connection 431 was actuallyanswered, since the outside network 407 only sees and interacts withuser device 410. The user device 410 preferably then does not send sucha notification 481 to the outside network 407 upon receiving a silencingcommand notification 462 (which can mean a number of things other thanincoming connection 431 being answered or accepted), but rather uponreceiving a call accepted or call answered notification 471.

At sequence event 490, the user device 410 can also provide a relay 491of the established connection from itself to the associated user device420A where the incoming connection 431 was answered, where the acceptedand established connection can then be handled for the user. This can bedone directly, or can be done by way of server 402 or another suitablegrouped device managing entity. At this point, the answering user device420A can be at a state 492 where it is handling the establishedconnection and no longer providing alerts, the user device 410 can be ata state 493 where it is relaying the connection from outside network 407to user device 420A and is no longer providing alerts, and all otheruser devices 420N can be at a state 494 where they are not acting on theincoming connection 431 at all, are aware that the incoming connection431 was answered, are no longer providing alerts, and may be aware thatthe incoming connection 431 was answered at user device 420A.

FIG. 5 illustrates a sequence diagram for an exemplary management of anincoming connection at a set of associated user devices having norelayed arrangement according to various embodiments of the presentdisclosure. Arrangement 500 can be similar to arrangement 400 above, inthat an outside network 507 can send incoming connections 531 toassociated user devices 520. Unlike relayed arrangement 400 above whereone of the user devices serves as a central device, however, non-relayedarrangement 500 can utilize a server 502 or another suitable groupeddevice communications managing entity that serves as the central deviceto receive the incoming connections 531. In still other embodiments,server 502 can represent a network that includes multiple servers, inwhich peer devices 520 each can register with an accessible server, suchthat some or all of the peer devices 520 may be registered with adifferent server. (Thus, there may be coordination between peer devices520 and between network resources, such as servers.) Accordingly, eachof the associated user devices 520 can be a peer device with respect toall of the other user devices, all of which collectively form a set ofassociated user devices.

In arrangement 500, each of user devices 520 can similarly be anywireless capable communication device, while incoming connection 531 canbe any suitable connection, as set forth above. At a first sequenceevent 530, an incoming connection 531 can be sent to a server 502 orsimilar entity from an outside network 507. Again for purposes ofdiscussion, incoming connection 531 can be referred to as a phone callor call, although any of the other types or forms of connections maysimilarly apply. At a following sequence event 540, the server 502 cannote that the incoming connection 531 is arriving and send notifications541 that the incoming connection 531 is arriving to each of theassociated user devices 520. Similar to the foregoing example, this canbe done by way of a push message sent using a WLAN communication, suchas Wi-Fi, for example. Accordingly, respective connection managers foreach of associated user devices 520 can receive a notification that theincoming connection 531 is arriving.

At sequence event 550, each of user devices 520 can note that theincoming connection 531 is arriving and, in response, can provide one ormore physical alert(s) that there is an incoming connection 531, candetermine whether the incoming connection 531 has been answered atitself, and can listen for communications from any of the other userdevices 520. Again, each of these processes can occur in parallel at agiven user device 520, and/or each of these processes can continue untilthe incoming connection 531 is gone, until the incoming connection 531is answered at one of the user devices 520, or until another endcondition occurs. Details regarding physical alerts, listening forcommunications, and multiple communication modes can all be the same asfor the foregoing embodiments from arrangement 400.

At sequence event 560, incoming connection 531 can be answered atassociated/peer user device 520B. This can represent, for example, aphone call being answered at a desktop computer associated with theserver 502 in one specific arrangement. Other arrangements mightalternatively apply, and it will be readily appreciated that incomingconnection 531 could instead have been answered at any of the other userdevices 520, with the following messages, events, and outcomes thenchanging correspondingly. When the incoming connection 531 is answeredat user device 520B, a connection manager for that user device 520B candetermine that the incoming connection 531 has indeed been answeredthere, can generate one or more silencing commands, and can transmit thesilencing command(s) using first and second wireless modes ofcommunication. The silencing command(s) can again take a variety offorms, such as embedded in a “call answered” push message and/orembedded in a BTLE alert or advertisement, for example.

Similar to the foregoing example, sequence event 560 can include a “callanswered” notification 561 that is sent from the user device 520B (e.g.,answering device) directly to the server 502, as well as a “silencingcommand” notification 562 that is sent from the user device 520B (e.g.,answering device) directly to the other user devices 520 (e.g.,non-answering devices). Again, notification 561 can be a push messagesent using a Wi-Fi or other WLAN communication, while notification 562can be a BTLE alert or advertisement sent using a WPAN communication,for example. Notification 562 containing a silencing command can bereceived as an incoming silencing command at each of non-answering userdevices 520, whereupon those devices (and answering user device 520B)can then stop providing physical alerts that incoming connection 531 isarriving and has not yet been answered. Accordingly, user device 520Bcan then be at a state 563 where the incoming connection 531 has beenanswered there and physical alerts regarding the incoming connection 531have been stopped, while each of non-answering user devices 520 can thenbe at a state 564 where physical alerts regarding the incomingconnection 531 have been stopped but they may not yet be aware ofwhether or where the incoming connection 531 was answered. Because ofdifferences in propagation and processing, silencing commands 562 may bereceived at and/or may cause the non-answering devices 520 to stopissuing physical alerts at different times.

At sequence event 570, the server 502 can note that the incomingconnection 531 has been answered and establish an accepted connectionwith the outside network 507. Server 502 can then provide a relay ortransfer 571 of the incoming connection 531 to user device 520B, wherethe incoming connection 531 can then be handled, e.g., by presentingaudio/video signals to the user. Server 502 can also send or forward“call answered” notifications 572 to each of non-answering user devices520. Again, these “call answered” notifications 572 can include anactual or inherent backup “silencing command,” in addition to other callanswered information, and can be send as push messages, such as using aWi-Fi or other WLAN connection. Again, the silencing commands cantypically be transmitted and received faster by way of secondcommunication mode direct BTLE alert notifications 562 than by way offirst communication mode push message combinations of notification 561and notification 572. At this point, the answering user device 520B canbe at a state 592 where it is handling the now established connectionfor incoming connection 531 and is no longer providing alerts, while allother non-answering user devices 520 can be at a state 594 where theyare not acting on the incoming connection 531 at all, are aware that theincoming connection 531 was answered, are no longer providing alerts,and may be aware that the incoming connection 531 was answered at userdevice 520B.

FIG. 6 illustrates a flowchart of an exemplary method performed by aconnection manager for managing outside connections on a set ofassociate user devices according to various embodiments of the presentdisclosure. The connection manager can execute on its respective givenuser device and can manage outside connections for its given user devicein particular amongst the set of associated user devices, which set caninclude the given user device. In various embodiments, each user devicein a set of associated user devices can have its own connection manager.Method 600 can start at step 602, where the connection manager canreceive a notification that an incoming connection is arriving at a userdevice. The incoming connection can be, for example, a voice call, avideo call, an Internet message, a teleconference, a push message, atext message, a data transfer, another suitable form of wirelesscommunication or any event for which there is a recurring alert ornotification, while the user device can be, for example, a smart phone,a tablet device, a wearable device, a portable media player, a laptopcomputer, or a desktop computer, among other possible wirelesscommunication devices.

At step 604, the connection manager can instruct one or more outputcomponents on the user device to provide connection alert(s), such asphysical alert(s) that the incoming connection is arriving and has notbeen answered. Again, this can involve ringing, flashing lights, visualmessages, haptic output, and the like. At step 606, the connectionmanager can listen for communications from any associated user device,which communications can be made using one or both of a first mode ofcommunication and a second mode of communication. As detailed above, thefirst mode of communication can involve indirect push messages usingWi-Fi or another WLAN connection, while the second mode of communicationcan involve direct BTLE advertisements or alerts using a WPANconnection, for example.

At decision step 608, the connection manager can determine whether asilencing command has been received. This can be, for example, where theconnection manager can receive an incoming silencing command from anassociated user device using the first mode of communication, the secondmode of communication, or both, and such a receipt can be a separatemethod step when it does take place. If such a silencing command hasbeen received, then the method skips to step 618, where the connectionmanager can instruct the one or more output components on its userdevice to stop providing the connection alert(s). If no silencingcommand has been received, however, then the method can continue todecision step 610.

At decision step 610, the connection manager can determine whether theincoming connection has been answered at its own user device. If not,then the method reverts to step 606, where the connection manager cancontinue to listen for associated device communications. In variousembodiments, decision steps 608 and 610 can be performed in parallel orin reverse order. In various embodiments, any or all of steps 604through 610 can be performed in parallel, which can continue until a yesis returned at step 608 or 610. When it is determined that the incomingconnection has been answered at its own user device at step 610, thenthe method can continue to step 612.

At step 612, the connection manager can generate a silencing command inresponse to the incoming connection being answered at its user device.At step 614, the connection manager can transmit the silencing commandusing the first wireless mode of communication (e.g., indirect pushmessaging) to be received at the associated user devices. Thistransmittal can be in the form of a “call answered” push messagenotification sent to a server, for example. At step 616, the connectionmanager can transmit the silencing command using the second wirelessmode of communication (e.g., direct BTLE alerts) to be received at theassociated user devices. This can be in the form of a “silencing commandonly” BTLE advertisement broadcast that goes directly to the other userdevices, for example.

At step 618, the connection manager can instruct the one or more outputcomponents on its user device to stop providing the connection alert(s).In various embodiments, all of steps 614 through 618 can be performedsimultaneously when the incoming connection is answered at the userdevice of the connection manager, and method 600 can end after anyinstance where step 618 is performed.

Moving next to FIG. 7, a sequence diagram is provided for an exemplarymanagement of an incoming connection at a set of associated user deviceshaving an active device according to various embodiments of the presentdisclosure. Arrangement 700 can be similar to arrangements 400 and 500above, in that an outside network 707 can send incoming connections 731to associated user devices 720. Unlike arrangements 400 and 500 above,however, arrangement 700 can include a situation where one of the userdevices is or has been designated as an “active device.” Such an “activedevice” designation can apply with similar effects to either of arelayed or non-relayed arrangement, as detailed above. Under any sucharrangement, a central user device (not shown) or a server 702 or othersuitable grouped device communications managing entity can serve as acentral device to receive the incoming connections 731. In the latterarrangement 700 as shown, each of the associated user devices 720 canagain be a peer device with respect to all of the other user devices,all of which collectively form a set of associated user devices.

An “active device” can be a designation that is given to whichever ofuser devices 720 is currently being used by a user, is currentlyprocessing, or is otherwise provided that status according to any ofvariety of settings or user preferences. This active device designationcan vary according to the type of incoming connection 730 in variousembodiments. In the event that two or more of user devices 720 arecurrently being used by a user, then a hierarchy chart or set ofpriority rules can be applied to determine which user device, if any,should be designated as the active device. For example, where a user isdetermined to be currently using his or her desktop computer only (e.g.,user device 720B), then that user device can be designated as the activedevice for all incoming connections 731. Where multiple user devices aresimultaneously in use, then a smart phone (e.g., user device 720A)currently in use might be designated as the active device for phonecalls, a desktop computer (e.g., user device 720B) currently in usemight be designated as the active device for e-mails, and so forth. Insome situations, none of user devices 720 might be designated as anactive device.

At an initial sequence event or other point in time prior to an incomingconnection 731 being made, one of the peer or associated user devices720 can be designated as an active device. This can be, for example,where user device 720A is designated with active device status at state729. Alternatively, or in addition, one or more active devicedesignations or determinations can be made by one or more systemcomponents, such as server 702, at the time that an incoming connection731 is made. As one example, user device 720A can be currently in use bythe user, such that it knows that it is an active device.

At sequence event 730, an incoming connection 731 can be sent to aserver 702 or similar entity from an outside network 707. Again forpurposes of discussion, incoming connection 731 can be referred to as aphone call or call, although any of the other types or forms ofconnections may similarly apply. At a following sequence event 740, theserver 702 can note that the incoming connection 731 is arriving andsend notifications 741 that the incoming connection 731 is arriving toeach of the associated user devices 720. Similar to the foregoingexample, this can be done by way of a push message sent using a WLANcommunication, such as Wi-Fi, for example. Accordingly, respectiveconnection managers for each of associated user devices 720 can receivea notification 741 that the incoming connection 731 is arriving.

At sequence event 750, each of non-active user devices 720B through 720Ncan note that the incoming connection 731 is arriving and in responsecan listen for communications from any of the other user devices 720,where such communications can again be by way of multiple communicationmodes, such as those detailed above. At this point, the communicationslistened for can include alert communications as to whether another ofthe other user devices 720 is an active device. In various embodimentsthat include such active device designations and features, thenon-active user devices 720B through 720N can delay providing physicalalerts for a short amount of time until it can be determined that noother user device is an active user device. Such active device listeningand alert delay embodiments can be combined with one or more of theforegoing embodiments in a manner that will be readily appreciated byone of skill in the art. If no active device alert communication isreceived for a short designated period of time, then any non-active userdevice can proceed as usual according to any of the foregoingembodiments. Such a short designated period of time can be, for example,slightly longer than the typical transmittal time for a direct BTLEadvertisement or alert communication (e.g., about 200 milliseconds). Theshort designated period of time might then be about 300-400milliseconds.

At sequence event 755, which can take place at the same time as sequenceevent 750, active user device 720A note that the incoming connection 731is arriving and can respond to notification 741 by sending out its ownnotifications 756 that it is an (or the) active user device. Thesenotifications 756 can be, for example, a BTLE advertisement or alertsent using a WPAN communication, for example. Notifications 756 can takethe form of a WPAN broadcast emitted periodically, occasionally, orcontinuously for a range of durations from less than one second up toapproximately ten seconds, e.g., for about two seconds in someimplementations. Again, this form of direct device to devicecommunication can be relatively fast, such that the transmittal time ison the order of about 200 milliseconds to every other non-active userdevice 720B through 720N. Notifications 756 can be received atnon-active user devices 720B through 720N, whereupon these user devicescan be put into a state 757. The active user device 720A can immediatelyenter a separate state 758 upon receiving notification 741 and knowingthat it is the active user device for incoming connection 731.

State 757 can include each respective non-active user device 720Bthrough 720N knowing that an incoming connection 731 is arriving, butthat another associated user device is an active device for at leastthat incoming connection 731. In various embodiments, this state 757 caninclude providing no incoming connection alerts at the non-activedevice, or it can include providing alerts, but limiting them to visualalerts (e.g., blinking light, caller ID) and/or haptic alerts (e.g.,vibrations) with no audible alerts (e.g., ringing). State 758 caninclude full alerts being provided at the active user device 720A. Invarious embodiments, each of the active and non-active user devices 720can then enter sequences where they wait and listen to see if and wherethe incoming connection is answered, such as at sequence events 450 or550 above.

FIG. 8 illustrates a flowchart of an exemplary method performed by aconnection manager for managing outside connections on a set ofassociated user devices having an active device according to variousembodiments of the present disclosure. Again, the connection manager canexecute on its respective given user device and can manage outsideconnections for its given user device in particular amongst the set ofassociated user devices, which set can include the given user device. Invarious embodiments, each user device in a set of associated userdevices can have its own connection manager. Method 800 can start atstep 802, where the connection manager can receive a notification thatan incoming connection is arriving at a user device. Again, the incomingconnection can be any such as those set forth above, and the user devicecan be any such as those set forth above.

At decision step 804, the connection manager can determine whether anyassociated user device is an active device. This can be done in thecontext of whether an active device assertion made by another associateduser device is superior to an active device assertion that could be madefor this user device. That is, where the connection manager might knowor determine that its own user device is an active device, anotherassertion or alert of an active device by an associated user devicemight be superior. For example, where a desktop computer is currently inuse and therefore active, an incoming active device alert or assertionfrom a smart phone can be considered a superior assertion when theincoming connection is a phone call. Of course, where the user devicefor the connection manager is not an active device, then any incomingnotification or alert that another associated user device is an activedevice would apply. Upon determining that another associated user deviceis active or has a superior claim to be an active device, then themethod can continue to step 812, where the connection manager caninstruct one or more output components on its user device to providevisual alert(s) only. When it is determined that no other active deviceclaim or superior active device claim applies, however, then the methodcontinues to decision step 806.

At decision step 806, the connection manager can determine whether itsown user device is an active device. If so, then the method continues tostep 808, where an active device notification can be generated andtransmitted. Again, this can be in the form of a BTLE alert oradvertisement that can be broadcast using a WPAN connection to all ofthe other associated user devices. The method can then continue to step810, where the connection manager can instruct one or more outputcomponents on its user device to provide audio alert(s), and step 812,where the connection manager can instruct its output component(s) toprovide visual alert(s) and/or haptic alert(s) as well. When step 810 isperformed, then step 812 can be performed in parallel in someembodiments.

Transitioning now to FIG. 9, an alternative exemplary system of wirelessnetworks and devices according to various embodiments of the presentdisclosure is illustrated in block diagram format. System 900 caninclude a receiving wireless communication user device 910 that can beinterconnected through several different wireless communicationtechnologies to an external set of networks and to two peripheral orassociated local wireless communication user devices 920A and 920B. Theuser device 910 can be a “central” device for WPAN purposes, and canreceive information from one or more packet switched networks and/orfrom one or more circuit switched networks, which is simply representedas a WWAN connection 908 provided through a wireless communicationnetwork 907. It will be appreciated that this can include more than onenetwork, and that WWAN connection 908 can be used to access a broadvariety of services (e.g., voice calls, text messages, data access,video calls, multimedia messaging, and media streaming). In addition,the user device 910 can use one or more WPAN connections 904 toperipheral or associated local wireless communication user devices 920Aand 920B. These user devices 920A and 920B may also be in communicationwith each other, such as using a WPAN connection 904, which can be aBluetooth® connection, for example.

In various embodiments, one or more of the user devices 910, 920A, 920Bcan include a processor, a memory, and a connection manager, among otherpossible components. The processor can be configured to implement theconnection manager on a given user device, and the connection managercan be configured to manage outside connections for the user device andthe other associated user devices. It will be understood that variousconnection functions that are or can be performed by a given user devicecan actually be performed by the connection manager for that userdevice. In some embodiments, one or more of the user devices 910, 920A,920B can be wirelessly paired or otherwise grouped or associated withall of the other user devices 910, 920A, 920B. For example, user device910 can be a smart phone or other communications device that iswirelessly paired with both of user devices 920A and 920B.

In various embodiments, the connection manager on a given user device910, 920A, 920B can serve to route connections between the user devices.For purposes of discussion, user device 910 can be a “central” wirelessuser device that receives outside connections, such that its connectionmanager can serve to route these connections and perform otherconnection related functions for all of the user devices 910, 920A, and920B. In some arrangements, user device 910 (e.g., its connectionmanager), can be adapted to receive outside connections, to receivesignals regarding various statuses of one or both of user devices 920Aand 920B, to route connections accordingly between the various userdevices 910, 920A, and 920B, to detect changes in the statuses of one orboth of user devices 920A and 920B, and to reroute connectionsaccordingly between the various user devices 910, 920A, and 920B.

Each of the peripheral or associated wireless communication user devices920A and 920B illustrated in FIG. 9 can provide output displaycapabilities as well as input response capabilities to allow a user ofthe user device 910 to interact with various services or otherwise relayconnections or communications therethrough, such as through one or bothof WPAN connections 904. For example, either of local wirelesscommunication user devices 920A or 920B can provide call relayfunctionality for an incoming phone call or other connection to userdevice 910, such that the user can accept an incoming call or otherconnection at any of user devices 910, 920A, or 920B. In one specificnon-limiting embodiment, user device 910 can be a smart phone, userdevice 920A can be a wireless headset and/or earbuds, and user device920B can be an electronic watch device or other such “wearable.”Accordingly, an incoming connection can be a telephone call. Of course,other types and arrangements of wireless communication devices can beused, and that fewer or more than two peripheral or associated userdevices 920A, 920B can be local wireless communication user devices thatare used with user device 910. As another example, one of the peripheralor associated user devices 920A, 920B can be a vehicle sound system.

In one specific non-limiting example, a status for a wireless headset(e.g., user device 920A) can dependent upon whether or not the wirelessheadset or at least a portion thereof is being worn by the user. Forexample, a status for a wireless headset can be “active” when an earbudor earpiece is in the ear of the user, and “inactive” when the earbud orearpiece is not in the ear of the user. As another example, anactive/inactive status for a vehicle sound system can be dependent uponwhether or not the vehicle electrical system is turned on. As yetanother example, a particular status for a peripheral or associated userdevice 920A, 920B can be determined with respect to a user input, suchas by a button press or voice command. A routing or rerouting functionperformed by a connection manager can then depend upon one or more ofthese various device statuses. For example, when a wireless headset oran earbud or earpiece thereof is being worn by the user, then theconnection manager can determine or detect this status and route anoutside connection accordingly. If the wireless headset is being worn bythe user, then the connection can be routed to the “active” headset, butif the wireless headset is not being worn by the user, then theconnection can be routed to the watch or other user device.

FIG. 10 illustrates a state diagram of exemplary states and transitionsfor the system of FIG. 9 according to various embodiments of the presentdisclosure. State system 1000 can include an initial state 1010, such aswhere an outside connection is to be routed to one of the variousassociated user devices. The outside connection can be an incomingconnection, such as a telephone call, or it can be a connection that isbeing initiated by one of the associated user devices. At this initialstate 1010, a determination can be made as to whether the connection isto be handled by the central user device (e.g., user device 910) or atthe set of associated user devices (e.g., user devices 920A and 920B).Determination 1011 can be for the connection to be handled at the mainor central user device, upon which that central user device then takesthe connection at state 1020. Conversely, determination 1012 can be forthe connection to be handled at the set of associated user devices, uponwhich state 1030 can be entered.

State 1030 can involve a determination as to whether a first associateduser device is currently paired with the central user device and whetherthe status of the first associated user device is active. For example,such a status can be active when the first associated user device is awireless headset that is being worn by the user. In the case that thewireless headset (i.e., first associated user device) is active and ispaired with the smart phone or other central user device, then theconnection can be routed to state 1040, where the connection is answeredby the central user device and routed to the active and paired firstassociated user device. If the status is not active and paired, however,then state 1035 is accessed, where a determination is made as to whetherthe first associated user device is active but not paired with thecentral user device. If that is the case, then state 1037 is accessed,but if the first associated user device is determined not to be activeat all, then state 1050 is accessed.

At either of states 1037 or 1050, the connection can be routed to thesecond associated user device, which again can be an electronic watch orother suitable wireless communications adapted user device. At state1037, the second associated user device can handle the routed connectionand communicate with the active first associated user device as itsaccessory device for the user. At state 1050, the second associated userdevice can handle the routed connection on its own for the user.

At state 1040, an event can involve a change in status for the firstassociated user device. A similar event can apply for state 1037. Eachof these events can involve, for example, the user taking off thewireless headset, which then changes the status from active to notactive. This then results in state 1050 being achieved. From state 1040,this can involve the connection being rerouted from the wireless headsetor other first associated communication device to the watch or othersecond associated communication device. From state 1037, this caninvolve the second associated user device no longer using the firstassociated user device as its accessory to handle the connection.

At state 1050, an event can similarly involve a change in status for thefirst associated user device, such as where the first associated userdevice goes from not active to active. For example, this can include theuser putting the wireless headset on (or the earbud or earpiece in hisor her ear), upon which state 1030 is then achieved. This can thenrevert back to the set of inquiries as to whether to reroute theconnection to the first associated user device, such as to arrive atstate 1040, or to arrive at state 1037 in the event that the firstassociated user device is not or remains unpaired with the central userdevice. The various states in state system 1000 can then continueaccording to the statuses of the first associated user device, which canchange over time. Various other statuses can also be used to determine astate change. For example, a user input at any of the central userdevice or the associated user devices can push or pull the connectionfrom one user device to another, such as at states 1040 or 1050. Suchuser inputs can also push or pull the connection back to the centraluser device, such as at state 1020.

FIG. 11 illustrates a flowchart of an exemplary method performed by aconnection manager on a user device for managing outside connections forthe user device and a set of associated user devices according tovarious embodiments of the present disclosure. Again, the connectionmanager can be located on a central user device, such as where outsideconnections are to be managed for the central user device and one ormore associated user devices. Method 1100 can start at a decision step1102, where the connection manager determines whether an outsideconnection is to be handled by the associated user devices. If not, thenthe method skips to step 1118, where the outside connection is handledat the central user device itself. If the outside connection is to behandled by the associate user devices, however, then the methodcontinues to step 1104.

At step 1104, the connection manager can receive a signal for the statusof a first associated user device, whereupon the connection manager candetermine whether the first associated user device is active or not atdecision step 1106. If the first associated user device is active, thenthe connection manager can route the connection to the first associateduser device at step 1108. If the first associated user device is notactive, however, then the connection manager can route the connection tothe second associated user device at step 1110.

At subsequent step 1112, the outside connection can then be handled atthe respective associated user device to which it has been routed. Atdecision step 1114, the connection manager can determine whether achange in the status of the first associated user device has beendetected. If so, then the method can revert to decision step 1106 sothat the connection can be rerouted to the other associated user deviceat the appropriate step 1108 or 1110. If not, then the method cancontinue to decision step 1116.

At decision step 1116, the connection manager can determine whether auser input has been received. If not, then the method can revert to step1112, where the connection can continue to be handled by the associateduser device to which it has been routed. If a user input has beenreceived at step 1116, however, then the method can continue to eitherof step 1106 or step 1118. Where the user input requires a push or apull to the other associated user device, then the method reverts backto step 1106 so that the connection can be rerouted accordingly at step1108 or 1110. Where the user input requires a push or a pull back to thecentral user device, however, then the method continues to step 1118,where this can take place.

For each of the foregoing flowcharts, it will be readily appreciatedthat not every step provided is always necessary, and that further stepsnot set forth herein may also be included. For example, added steps thatinvolve specific time determinations for given commands or alerts to bebroadcast may be added. Also, steps that provide more detail withrespect to various system components or features could also be added.Furthermore, the exact order of steps may be altered as desired, andsome steps may be performed simultaneously.

FIG. 12 illustrates in block diagram format an exemplary computingdevice 1200 that can be used to implement the various components andtechniques described herein, according to some embodiments. Inparticular, the detailed view illustrates various components that can beincluded in the user device 110 illustrated in FIG. 1. As shown in FIG.12, the computing device 1200 can include a processor 1202 thatrepresents a microprocessor or controller for controlling the overalloperation of computing device 1200. The computing device 1200 can alsoinclude a user input device 1208 that allows a user of the computingdevice 1200 to interact with the computing device 1200. For example, theuser input device 1208 can take a variety of forms, such as a button,keypad, dial, touch screen, audio input interface, visual/image captureinput interface, input in the form of sensor data, etc. Still further,the computing device 1200 can include a display 1210 (screen display)that can be controlled by the processor 1202 to display information tothe user (for example, caller ID or other information relating to acurrent telephone call). A data bus 1216 can facilitate data transferbetween at least a storage device 1240, the processor 1202, and acontroller 1213. The controller 1213 can be used to interface with andcontrol different equipment through and equipment control bus 1214. Thecomputing device 1200 can also include a network/bus interface 1211 thatcouples to a data link 1212. In the case of a wireless connection, thenetwork/bus interface 1211 can include a wireless transceiver.

The computing device 1200 also include a storage device 1240, which cancomprise a single storage or a plurality of storages (e.g., harddrives), and includes a storage management module that manages one ormore partitions within the storage device 1240. In some embodiments,storage device 1240 can include flash memory, semiconductor (solidstate) memory or the like. The computing device 1200 can also include aRandom Access Memory (“RAM”) 1220 and a Read-Only Memory (“ROM”) 1222.The ROM 1222 can store programs, utilities or processes to be executedin a non-volatile manner. The RAM 1220 can provide volatile datastorage, and stores instructions related to the operation of thecomputing device 1200.

The various aspects, embodiments, implementations or features of thedescribed embodiments can be used separately or in any combination.Various aspects of the described embodiments can be implemented bysoftware, hardware or a combination of hardware and software. Thedescribed embodiments can also be embodied as computer readable code ona computer readable medium. The computer readable medium is any datastorage device that can store data which can thereafter be read by acomputer system. Examples of the computer readable medium includeread-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape,hard storage drives, solid state drives, and optical data storagedevices. The computer readable medium can also be distributed overnetwork-coupled computer systems so that the computer readable code isstored and executed in a distributed fashion.

Some embodiments provide a method for managing connections performed bya processor on a user device. During the method, the user device maygenerate a silencing command when an incoming connection has beenanswered at the user device, where each of the user device and one ormore associated user devices is adapted to answer the incomingconnection. Then, the user device may transmit the silencing commandusing a first mode of communication to the one or more associated userdevices. Moreover, the user device may transmit the silencing commandusing a second mode of communication to the one or more associated userdevices, where the second mode of communication differs from the firstmode of communication such that the silencing command transmitted usingthe second mode of communication incurs less delay than the silencingcommand transmitted using the first mode of communication.

Note that the incoming connection may be a voice call.

Moreover, the first mode of communication may define an indirectcommunication path from the user device to the one or more associateduser devices, and the second mode of communication may define a directcommunication path from the user device to the one or more associateduser devices. For example, the first mode of communication may include awirelessly transmitted push message that communicates via a networkbased server before reaching the one or more associated user devices,and the second mode of communication may include a wirelesslytransmitted BTLE advertisement.

Furthermore, a transmittal time using the second mode of communicationmay be less than 200 milliseconds.

Additionally, before generating the silencing command, the user devicemay: receive a notification indicating the incoming connection; instructone or more output components of the user device to provide an alertindicating the incoming connection; and listen for communications fromthe one or more associated user devices using both the first mode ofcommunication and the second mode of communication. In some embodiments,the user device: receives an incoming silencing command from one of theone or more associated user devices using the first mode ofcommunication, the second mode of communication, or both; and instructsthe one or more output components to stop providing the alert indicatingthe incoming connection after receiving the incoming silencing command.Note that the user device may receive the incoming silencing command inresponse to the incoming connection being answered at one of the one ormore associated user devices.

Moreover, the user device may: determine whether any of the one or moreassociated user devices is currently active; and limit the alert tovisual alerts when one of the one or more associated user devices iscurrently active.

Furthermore, the user device may determine whether the user deviceanswers the incoming connection.

Additionally, each of the user device and the one or more associateduser devices may be selected from a group that includes: a smart phone,a tablet device, a wearable device, a portable media player, a laptopcomputer, and/or a desktop computer.

Another embodiment provides the user device that manages outsideconnections. This user device may include a processor that implements aconnection manager, which may perform at least some of theaforementioned operations in the method. During operation, theconnection manager may determine whether the user device answers anincoming outside connection, where each of the user device and one ormore associated user devices is adapted to answer the incoming outsideconnection. Then, the connection manager may generate a silencingcommand when the incoming outside connection has been answered at theuser device. Moreover, the connection manager may transmit the silencingcommand using a first mode of communication to the one or moreassociated user devices, and may transmit the silencing command using asecond mode of communication to the one or more associated user devices.Note that the second mode of communication may differ from the firstmode of communication such that the silencing command transmitted usingthe second mode of communication incurs less delay than the silencingcommand transmitted using the first mode of communication.

Another embodiment provides a non-transitory computer readable storagemedium configured to store instructions that, when executed by aprocessor included in a user device, cause the user device to implementa connection manager. The connection manager may perform at least someof the aforementioned operations in the method. During operation theconnection manager may receive a notification indicating an incomingconnection, where each of the user device and one or more associateduser devices is adapted to answer the incoming connection. Then, theconnection manager may listen for communications from the one or moreassociated user devices using both a first mode of communication and asecond mode of communication, where the second mode of communicationdiffers from the first mode of communication such that a communicationtransmitted using the second mode of communication incurs less delaythan the communication transmitted using the first mode ofcommunication. Moreover, the connection manager may determine whetherany of the one or more associated user devices is currently active.Furthermore, the connection manager may instruct one or more outputcomponents of the user device to provide an alert indicating theincoming connection, where the alert is limited to visual alerts whenone of the one or more associated user devices is currently active.Next, the connection manager may determine whether the user deviceanswers the incoming connection. When the user device answers theincoming connection, the connection manager may: generate a silencingcommand; transmit the silencing command using the first mode ofcommunication to the one or more associated user devices; and transmitthe silencing command using the second mode of communication to the oneor more associated user devices. Otherwise, the connection manager may:receive an incoming silencing command from one of the one or moreassociated user devices using the first mode of communication, thesecond mode of communication, or both; and instruct the one or moreoutput components to stop providing the alert indicating the incomingconnection after receiving the incoming silencing command.

Another embodiment provides a system that includes the user device.

Some embodiments provide a user device that manages outside connections.This user device may include a processor that implements a connectionmanager. During operation, the connection manager may receive a signalregarding the status of a first associated user device. Then, theconnection manager may route an outside connection from the user deviceto the first associated user device over a wireless mode ofcommunication when the status of the first associated user device isactive. Otherwise, the connection manager may route the outsideconnection from the user device to a second associated user device.Next, the connection manager may detect a change in the status of thefirst associated user device after the outside connection has beenrouted to the first associated user device or the second associated userdevice. Moreover, the connection manager may reroute the outsideconnection from one of the first associated user device and the secondassociated user device to the other of the first associated user deviceand the second associated user device over the wireless mode ofcommunication when a change in the status of the first associated userdevice is detected.

Note that the outside connection may be a telephone call. Moreover, theuser device may be a smart phone. Furthermore, the first associated userdevice may be a headset. The headset status may be active when at leasta portion of the headset is being worn by the user. Additionally, thesecond associated user device may be a watch.

In some embodiments, the connection manager: receives an input made bythe user on the second associated user device; and reroutes the outsideconnection from one of the first associated user device and the secondassociated user device to the other of the first associated user deviceand the second associated user device over the wireless mode ofcommunication when the input is received.

Moreover, the first associated user device may be a vehicle soundsystem.

Furthermore, the wireless mode of communication may include a Bluetooth®connection.

Additionally, the connection manager may determine whether the outsideconnection is to be handled for a user at the user device or at the setof associated user devices.

Note that the headset status may be active when at least a portion ofthe headset is being worn by the user.

Furthermore, the connection manager may: receive an input made by theuser on the user device, the first associated user device, or the secondassociated user device; and reroute the outside connection from one ofthe first associated user device and the second associated user deviceback to the user device when the input is received.

Additionally, the connection manager may determine whether the outsideconnection is to be handled for a user at the user device or at the setof associated user devices.

Another embodiment provides a method performed by a connection managerfor managing connections on a user device. This method may include atleast some of the aforementioned operations performed by the userdevice. For example, during the method, the connection manager may routean outside connection from the user device to a first associated userdevice when a status of the first associated user device comprises afirst status. Otherwise, the connection manager may route the outsideconnection from the user device to a second associated user device.Then, the connection manager may detect a change in the status of thefirst associated user device after the outside connection has beenrouted to the first associated user device or the second associated userdevice. Moreover, the connection manager may reroute the outsideconnection from one of the first associated user device and the secondassociated user device to the other of the first associated user deviceand the second associated user device when a change in the status of thefirst associated user device is detected.

Another embodiment provides a non-transitory computer readable storagemedium configured to store instructions that, when executed by aprocessor included in a user device, cause the user device to implementa connection manager that to manages outside connections for the userdevice and a set of associated user devices. The connection manager mayperform at least some of the aforementioned operations in the method.During operation the connection manager may receive a signal regardingthe status of a first associated user device. Then, the connectionmanager may route an outside connection from the user device to thefirst associated user device over a wireless mode of communication whenthe status of the first associated user device is active. Otherwise, theconnection manager may route the outside connection from the user deviceto a second associated user device. Moreover, the connection manager maydetect a change in the status of the first associated user device afterthe outside connection has been routed to the first associated userdevice or the second associated user device. Next, the connectionmanager may reroute the outside connection from one of the firstassociated user device and the second associated user device to theother of the first associated user device and the second associated userdevice over the wireless mode of communication when a change in thestatus of the first associated user device is detected.

Another embodiment provides a system that includes the user device.

Another embodiment provides the user device that manages outsideconnections. This user device may include a processor that implements aconnection manager. During operation, the connection manager receives anincoming connection alert associated with an incoming connection. Then,the connection manager determines when the incoming connection isanswered at the user device or one or more associated user device, wherethe one or more associated user devices are capable of answering theincoming connection. Moreover, the connection manager generates asilencing command based on the determination. Next, the connectionmanager transmits the silencing command to the one or more associateduser devices using a first mode of communication.

Note that the first mode of communication may include wirelesscommunication having a range less than a predefined value. For example,the first mode of communication may include a Bluetooth alert or aBluetooth advertisement.

Moreover, the transmitting may involve broadcasting the silencingcommand to the one or more associated user devices.

Furthermore, the connection manager may transmit the silencing commandto the one or more associated user devices using a second mode ofcommunication that is different from the first mode of communication.For example, the second mode of communication may have a transmittaltime that is longer than the first mode of communication. In particular,the second mode of communication may include a push message.

Additionally, the silencing command may is included in a call answernotification.

In some embodiments, the connection manager transmits a call answernotification that indicates that the incoming connection has beenanswered.

Moreover, the connection manager may receive another call answernotification from one of the one or more associated user devices.

Furthermore, the silencing command may instruct separate connectionmanagers located on the one or more associated user devices to stopproviding incoming connection alerts about the incoming connection.

Another embodiment provides a method performed by a connection managerfor managing connections on a user device. This method may include atleast some of the aforementioned operations performed by the userdevice.

Another embodiment provides a non-transitory computer readable storagemedium configured to store instructions that, when executed by aprocessor included in a user device, cause the user device to implementa connection manager that to manages outside connections for the userdevice and a set of associated user devices. The connection manager mayperform at least some of the aforementioned operations in the method.

Another embodiment provides a system that includes the user device.

The foregoing description, for purposes of explanation, used specificnomenclature to provide a thorough understanding of the describedembodiments. However, it will be apparent to one skilled in the art thatthe specific details are not required in order to practice the describedembodiments. Thus, the foregoing descriptions of specific embodimentsare presented for purposes of illustration and description. They are notintended to be exhaustive or to limit the described embodiments to theprecise forms disclosed. It will be apparent to one of ordinary skill inthe art that many modifications and variations are possible in view ofthe above teachings.

What is claimed is:
 1. A method for managing connections performed by aserver, the method comprising: by the server: receiving, from anexternal network, a notification indicating an incoming connection for aset of two or more associated user devices adapted to answer theincoming connection; sending, to the set of two or more associated userdevices, a notification of the incoming connection; listening forcommunication from the set of two or more associated user devices;receiving, from a first user device of the set of two or more associateduser devices, an indication answering the incoming connection; relayingthe incoming connection to the first user device responsive to receiptof the indication answering the incoming connection; and sending, toeach user device of the set of two or more associated user devices otherthan the first user device via a first mode of communication, a pushmessage comprising an indication that the incoming connection wasanswered, wherein: each of the two or more associated user devices areassociated with a common user account, and the first user device sendsto at least one other associated user device a silencing command via asecond mode of communication.
 2. The method as recited in claim 1,wherein the two or more associated user devices are registered with thecommon user account at the server.
 3. The method as recited in claim 1,wherein the indication that the incoming connection was answered causesthe two or more associated user devices to determine not to issue anyfurther alerts for the incoming connection.
 4. The method as recited inclaim 1, wherein the push message includes an explicit silencingcommand.
 5. The method as recited in claim 1, wherein the indicationthat the incoming connection was answered is interpreted as an implicitsilencing command by the two or more associated user devices.
 6. Themethod as recited in claim 1, wherein the indication that the incomingconnection was answered informs the two or more associated user devicesthat the first user device answered the incoming connection.
 7. Themethod as recited in claim 1, wherein: the first mode of communicationcomprises a non-cellular wireless local area network; and the secondmode of communication comprises a non-cellular personal area network. 8.The method as recited in claim 1, further comprising: by the server:establishing a connection with the external network for the incomingconnection before relaying the incoming connection to the first userdevice.
 9. An apparatus configurable for operation in a server, theapparatus comprising: a processor communicatively coupled to a memorystoring instructions that, when executed by the processor, cause theserver to perform actions including: receiving, from an externalnetwork, a notification indicating an incoming connection for a set oftwo or more associated user devices adapted to answer the incomingconnection; sending, to the set of two or more associated user devices,a notification of the incoming connection; listening for communicationfrom the set of two or more associated user devices; receiving, from afirst user device of the set of two or more associated user devices, anindication answering the incoming connection; relaying the incomingconnection to the first user device responsive to receipt of theindication answering the incoming connection; and sending, to each userdevice of the set of two or more associated user devices other than thefirst user device via a first mode of communication, a push messagecomprising an indication that the incoming connection was answered,wherein: each of the two or more associated user devices are associatedwith a common user account, and the first user device sends to at leastone other associated user device a silencing command via a second modeof communication.
 10. The apparatus as recited in claim 9, wherein thetwo or more associated user devices are registered with the common useraccount at the server.
 11. The apparatus as recited in claim 9, whereinthe indication that the incoming connection was answered causes the twoor more associated user devices to determine not to issue any furtheralerts for the incoming connection.
 12. The apparatus as recited inclaim 9, wherein the push message includes an explicit silencingcommand.
 13. The apparatus as recited in claim 9, wherein the indicationthat the incoming connection was answered is interpreted as an implicitsilencing command by the two or more associated user devices.
 14. Theapparatus as recited in claim 9, wherein the indication that theincoming connection was answered informs the two or more associated userdevices that the first user device answered the incoming connection. 15.The apparatus as recited in claim 9, wherein execution of theinstructions by the processor further causes the server to: establish aconnection with the external network for the incoming connection beforerelaying the incoming connection to the first user device.
 16. A serverfor managing connections for a set of two or more associated userdevices, the server comprising: a transceiver for wireless configurablefor communication with the set of two or more associated user devices;and processing circuitry, including a processor and a memory storinginstructions, communicatively coupled to the transceiver, whereinexecution of the instructions by the processor causes the server toperform actions including: receiving, from an external network, anotification indicating an incoming connection for the set of two ormore associated user devices adapted to answer the incoming connection;sending, to the set of two or more associated user devices, anotification of the incoming connection; listening for communicationfrom the set of two or more associated user devices; receiving, from afirst user device of the set of two or more associated user devices, anindication answering the incoming connection; relaying the incomingconnection to the first user device responsive to receipt of theindication answering the incoming connection; and sending, to each userdevice of the set of two or more associated user devices other than thefirst user device via a first mode of communication, a push messagecomprising an indication that the incoming connection was answered,wherein: each of the two or more associated user devices are associatedwith a common user account, and the first user device sends to at leastone other associated user device a silencing command via a second modeof communication.
 17. The apparatus as recited in claim 9, wherein: thefirst mode of communication comprises a non-cellular wireless local areanetwork; and the second mode of communication comprises a non-cellularpersonal area network.
 18. The server as recited in claim 16, whereinthe indication that the incoming connection was answered causes the twoor more associated user devices to determine not to issue any furtheralerts for the incoming connection.
 19. The server as recited in claim16, wherein the indication that the incoming connection was answeredinforms the two or more associated user devices that the first userdevice answered the incoming connection.
 20. The server as recited inclaim 16, wherein: the first mode of communication comprises anon-cellular wireless local area network; and the second mode ofcommunication comprises a non-cellular personal area network.